-
Notifications
You must be signed in to change notification settings - Fork 669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: bypass Qt's QFile::encodeName() in csync #12039
base: master
Are you sure you want to change the base?
Conversation
849a1ca
to
1b2d2ca
Compare
a70dda3
to
980bd4a
Compare
I moved "Clarify propagator job descriptions" out as a seperate PR: #12050 . We can merge the |
a74d10d
to
44b4a8c
Compare
test/testlocaldiscovery.cpp
Outdated
|
||
// Test that when a file/directory name on the remote is encoded in NFC, the local name is encoded | ||
// in the same way, and that a subsequent sync does not change anything. And the same for NFD. | ||
void testNameEncoding() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@erikjv Please document what exactly this test is about. Also thinking about that the function name testNameEncoding()
is not giving that much of an explanation. THX
44b4a8c
to
a609ad5
Compare
a609ad5
to
ca99d6b
Compare
ab3e219
to
4504d25
Compare
…File::encodeName()
To prevent `QFile::rename` doing normalization changes to the file name.
Check that a file/directory name with NFC encoding on the server ends up with the same encoding on the client, and that a subsequent discovery+sync will not upload differently encoded files. Same for an NFD encoded file/directory name.
4504d25
to
f978da9
Compare
ToDo